Repository navigation
docs(roadmap): add reusable fork-local capability Issue template - #38
Merged
xLagerFeuer merged 1 commit intoNov 17, 2026
Merged
Conversation
Separate source-grounded internal discussion from external maintainer-facing architecture issues. Preserve PLAN_ONLY, case-local evidence, original issue dedupe, native alternatives and independent publication approvals.
xLagerFeuer
deleted the
docs/generic-fork-roadmap-issue-template-20261117
branch
November 17, 2026 21:03
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add a generic Issue template for OpenSiro's own working fork, usable by
upstream roadmap OWNER/REPOregardless of the chosen original or VSM function. This is not a specific Paperclip roadmap, a new external publication, or a change to the existing external architecture Issue template.Contract
Conly with a separate constructor/acceptance contract if justified, optional parent/autonomous modes not universal requirements.NOT_MEASUREDuntil supported.opensiro-contributions/<fork>@opensiro/meta:.opensiro/issues/<case-id>/; public GitHub fork Issue and public original Issue each require separate exact approval. Original Issue dedupe and no implied cross-owner native transfer or code implementation.Files
templates/FORK_CAPABILITY_ROADMAP_ISSUE.md— new 7-section fill-in, project-neutral GitHub Issue body for the working fork.PROTOCOL.md,docs/CAPABILITY_ROADMAP.md— link new internal Issue template alongside distinct existingtemplates/EXTERNAL_ARCHITECTURE_ISSUE.md.tests/test_fork_roadmap_issue_template.py— assertions for generalized format, evidence/cost gates, artifact ownership and separate-publication limits.CHANGELOG.md— unreleased note.No existing Paperclip/Browser Harness artifacts or code changed. No GitHub Issue or original-repository interaction published. No version bump.